Turnbull China Bikeride

home *** CD-ROM | disk | FTP | other *** search

/ Turnbull China Bikeride / Turnbull China Bikeride - Disc 1.iso / ARGONET / PD / PROGRAMMING / PERL.SPK / Perl5001 / Manual / perldiag_h < prev next >

Wrap

Text File | 1995-04-18 | 76KB | 2,170 lines

<HTML> <TITLE> PERLDIAG </TITLE> <h2>NAME</h2> perldiag - various Perl diagnostics <h2>DESCRIPTION</h2> These messages are classified as follows (listed in increasing order of desperation): <pre> (W) A warning (optional). (D) A deprecation (optional). (S) A severe warning (mandatory). (F) A fatal error (trappable). (P) An internal error you should never see (trappable). (X) A very fatal error (non-trappable). </pre> Optional warnings are enabled by using the <A HREF="perlrun.html#perlrun_362">-w</A> switch. Trappable errors may be trapped using the eval operator. See perlfunc/eval. Some of these messages are generic. Spots that vary are denoted with a %s, just as in a printf format. Note that some message start with a %s! The symbols "%-?@ sort before the letters, while [ and \ sort after. <dl> <dt>"my" variable %s can't be in a package <dd> (F) Lexically scoped variables aren't in a package, so it doesn't make sense to try to declare one with a package qualifier on the front. Use local() if you want to localize a package variable. </dd> <dt>"no" not allowed in expression <dd> (F) The "no" keyword is recognized and executed at compile time, and returns no useful value. See <A HREF="perlmod.html"> the perlmod manpage</A> . </dd> <dt>"use" not allowed in expression <dd> (F) The "use" keyword is recognized and executed at compile time, and returns no useful value. See <A HREF="perlmod.html"> the perlmod manpage</A> . </dd> <dt>% may only be used in unpack <dd> (F) You can't pack a string by supplying a checksum, since the checksumming process loses information, and you can't go the other way. See perlfunc/unpack. </dd> <dt>%s (...) interpreted as function <dd> (W) You've run afoul of the rule that says that any list operator followed by parentheses turns into a function, with all the list operators arguments found inside the parens. See perlop/Terms and List Operators (Leftward). </dd> <dt>%s argument is not a HASH element <dd> (F) The argument to delete() or exists() must be a hash element, such as </dd> <pre> $foo{$bar} $ref->[12]->{"susie"} </pre> <dt>%s did not return a true value <dd> (F) A required (or used) file must return a true value to indicate that it compiled correctly and ran its initialization code correctly. It's traditional to end such a file with a "1;", though any true value would do. See perlfunc/require. </dd> <dt>%s found where operator expected <dd> (S) The Perl lexer knows whether to expect a term or an operator. If it sees what it knows to be a term when it was expecting to see an operator, it gives you this warning. Usually it indicates that an operator or delimiter was omitted, such as a semicolon. </dd> <dt>%s had compilation errors. <dd> (F) The final summary message when a perl -c fails. </dd> <dt>%s has too many errors. <dd> (F) The parser has given up trying to parse the program after 10 errors. Further error messages would likely be uninformative. </dd> <dt>%s matches null string many times <dd> (W) The pattern you've specified would be an infinite loop if the regular expression engine didn't specifically check for that. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>%s never introduced <dd> (S) The symbol in question was declared but somehow went out of scope before it could possibly have been used. </dd> <dt>%s syntax OK <dd> (F) The final summary message when a perl -c succeeds. </dd> <dt><A HREF="perlrun.html#perlrun_355">-P</A> not allowed for setuid/setgid script <dd> (F) The script would have to be opened by the C preprocessor by name, which provides a race condition that breaks security. </dd> <dt><A HREF="perlrun.html#perlrun_358">-T</A> and -B not implemented on filehandles <dd> (F) Perl can't peek at the stdio buffer of filehandles when it doesn't know about your kind of stdio. You'll have to use a filename instead. </dd> <dt>?+* follows nothing in regexp <dd> (F) You started a regular expression with a quantifier. Backslash it if you meant it literally. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>@ outside of string <dd> (F) You had a pack template that specified an absolution position outside the string being unpacked. See perlfunc/pack. </dd> <dt>accept() on closed fd <dd> (W) You tried to do an accept on a closed socket. Did you forget to check the return value of your socket() call? See perlfunc/accept. </dd> <dt>Allocation too large: %lx <dd> (F) You can't allocate more than 64K on an MSDOS machine. </dd> <dt>Arg too short for msgsnd <dd> (F) msgsnd() requires a string at least as long as sizeof(long). </dd> <dt>Args must match #! line <dd> (F) The setuid emulator requires that the arguments Perl was invoked with match the arguments specified on the #! line. </dd> <dt>Argument "%s" isn't numeric <dd> (W) The indicated string was fed as an argument to an operator that expected a numeric value instead. If you're fortunate the message will identify which operator was so unfortunate. </dd> <dt>Array @%s missing the @ in argument %d of %s() <dd> (D) Really old Perl let you omit the @ on array names in some spots. This is now heavily deprecated. </dd> <dt>assertion botched: %s <dd> (P) The malloc package that comes with Perl had an internal failure. </dd> <dt>Assertion failed: file "%s" <dd> (P) A general assertion failed. The file in question must be examined. </dd> <dt>Assignment to both a list and a scalar <dd> (F) If you assign to a conditional operator, the 2nd and 3rd arguments must either both be scalars or both be lists. Otherwise Perl won't know which context to supply to the right side. </dd> <dt>Attempt to free non-arena SV: 0x%lx <dd> (P) All SV objects are supposed to be allocated from arenas that will be garbage collected on exit. An SV was discovered to be outside any of those arenas. </dd> <dt>Attempt to free temp prematurely <dd> (W) Mortalized values are supposed to be freed by the free_tmps() routine. This indicates that something else is freeing the SV before the free_tmps() routine gets a chance, which means that the free_tmps() routine will be freeing an unreferenced scalar when it does try to free it. </dd> <dt>Attempt to free unreferenced glob pointers <dd> (P) The reference counts got screwed up on symbol aliases. </dd> <dt>Attempt to free unreferenced scalar <dd> (W) Perl went to decrement the reference count of a scalar to see if it would go to 0, and discovered that it had already gone to 0 earlier, and should have been freed, and in fact, probably was freed. This could indicate that SvREFCNT_dec() was called too many times, or that SvREFCNT_inc() was called too few times, or that the SV was mortalized when it shouldn't have been, or that memory has been corrupted. </dd> <dt>Bad arg length for %s, is %d, should be %d <dd> (F) You passed a buffer of the wrong size to one of msgctl(), semctl() or shmctl(). In C parlance, the correct sized are, respectively, sizeof(struct msqid_ds *), sizeof(struct semid_ds *) and sizeof(struct shmid_ds *). </dd> <dt>Bad associative array <dd> (P) One of the internal hash routines was passed a null HV pointer. </dd> <dt>Bad filehandle: %s <dd> (F) A symbol was passed to something wanting a filehandle, but the symbol has no filehandle associated with it. Perhaps you didn't do an open(), or did it in another package. </dd> <dt>Bad free() ignored <dd> (S) An internal routine called free() on something that had never been malloc()ed in the first place. </dd> <dt>Bad name after %s:: <dd> (F) You started to name a symbol by using a package prefix, and then didn't finish the symbol. In particular, you can't interpolate outside of quotes, so </dd> <pre> $var = 'myvar'; $sym = mypack::$var; </pre> is not the same as <pre> $var = 'myvar'; $sym = "mypack::$var"; </pre> <dt>Bad symbol for array <dd> (P) An internal request asked to add an array entry to something that wasn't a symbol table entry. </dd> <dt>Bad symbol for filehandle <dd> (P) An internal request asked to add a filehandle entry to something that wasn't a symbol table entry. </dd> <dt>Bad symbol for hash <dd> (P) An internal request asked to add a hash entry to something that wasn't a symbol table entry. </dd> <dt>BEGIN failed--compilation aborted <dd> (F) An untrapped exception was raised while executing a BEGIN subroutine. Compilation stops immediately and the interpreter is exited. </dd> <dt>bind() on closed fd <dd> (W) You tried to do a bind on a closed socket. Did you forget to check the return value of your socket() call? See perlfunc/bind. </dd> <dt>Callback called exit <dd> (F) A subroutine invoked from an external package via perl_call_sv() exited by calling exit. </dd> <dt>Can't "last" outside a block <dd> (F) A "last" statement was executed to break out of the current block, except that there's this itty bitty problem called there isn't a current block. Note that an "if" or "else" block doesn't count as a "loopish" block. You can usually double the curlies to get the same effect though, since the inner curlies will be considered a block that loops once. See perlfunc/last. </dd> <dt>Can't "next" outside a block <dd> (F) A "next" statement was executed to reiterate the current block, but there isn't a current block. Note that an "if" or "else" block doesn't count as a "loopish" block. You can usually double the curlies to get the same effect though, since the inner curlies will be considered a block that loops once. See perlfunc/last. </dd> <dt>Can't "redo" outside a block <dd> (F) A "redo" statement was executed to restart the current block, but there isn't a current block. Note that an "if" or "else" block doesn't count as a "loopish" block. You can usually double the curlies to get the same effect though, since the inner curlies will be considered a block that loops once. See perlfunc/last. </dd> <dt>Can't bless non-reference value <dd> (F) Only hard references may be blessed. This is how Perl "enforces" encapsulation of objects. See <A HREF="perlobj.html"> the perlobj manpage</A> . </dd> <dt>Can't break at that line <dd> (S) A warning intended for while running within the debugger, indicating the line number specified wasn't the location of a statement that could be stopped at. </dd> <dt>Can't call method "%s" in empty package "%s" <dd> (F) You called a method correctly, and it correctly indicated a package functioning as a class, but that package doesn't have ANYTHING defined in it, let alone methods. See <A HREF="perlobj.html"> the perlobj manpage</A> . </dd> <dt>Can't call method "%s" on unblessed reference <dd> (F) A method call must know what package it's supposed to run in. It ordinarily finds this out from the object reference you supply, but you didn't supply an object reference in this case. A reference isn't an object reference until it has been blessed. See <A HREF="perlobj.html"> the perlobj manpage</A> . </dd> <dt>Can't call method "%s" without a package or object reference <dd> (F) You used the syntax of a method call, but the slot filled by the object reference or package name contains an expression that returns neither an object reference nor a package name. (Perhaps it's null?) Something like this will reproduce the error: </dd> <pre> $BADREF = undef; process $BADREF 1,2,3; $BADREF->process(1,2,3); </pre> <dt>Can't chdir to %s <dd> (F) You called perl -x/foo/bar, but /foo/bar is not a directory that you can chdir to, possibly because it doesn't exist. </dd> <dt>Can't coerce %s to integer in %s <dd> (F) Certain types of SVs, in particular real symbol table entries (type GLOB), can't be forced to stop being what they are. So you can't say things like: </dd> <pre> *foo += 1; </pre> You CAN say <pre> $foo = *foo; $foo += 1; </pre> but then $foo no longer contains a glob. <dt>Can't coerce %s to number in %s <dd> (F) Certain types of SVs, in particular real symbol table entries (type GLOB), can't be forced to stop being what they are. </dd> <dt>Can't coerce %s to string in %s <dd> (F) Certain types of SVs, in particular real symbol table entries (type GLOB), can't be forced to stop being what they are. </dd> <dt>Can't create pipe mailbox <dd> (F) An error peculiar to VMS. </dd> <dt>Can't declare %s in my <dd> (F) Only scalar, array and hash variables may be declared as lexical variables. They must have ordinary identifiers as names. </dd> <dt>Can't do inplace edit on %s: %s <dd> (S) The creation of the new file failed for the indicated reason. </dd> <dt>Can't do inplace edit without backup <dd> (F) You're on a system such as MSDOS that gets confused if you try reading from a deleted (but still opened) file. You have to say <A HREF="perlrun.html#perlrun_350">-i</A> .bak, or some such. </dd> <dt>Can't do inplace edit: %s > 14 characters <dd> (S) There isn't enough room in the filename to make a backup name for the file. </dd> <dt>Can't do inplace edit: %s is not a regular file <dd> (S) You tried to use the <A HREF="perlrun.html#perlrun_350">-i</A> switch on a special file, such as a file in /dev, or a FIFO. The file was ignored. </dd> <dt>Can't do setegid! <dd> (P) The setegid() call failed for some reason in the setuid emulator of suidperl. </dd> <dt>Can't do seteuid! <dd> (P) The setuid emulator of suidperl failed for some reason. </dd> <dt>Can't do setuid <dd> (F) This typically means that ordinary perl tried to exec suidperl to do setuid emulation, but couldn't exec it. It looks for a name of the form sperl5.000 in the same directory that the perl executable resides under the name perl5.000, typically /usr/local/bin on Unix machines. If the file is there, check the execute permissions. If it isn't, ask your sysadmin why he and/or she removed it. </dd> <dt>Can't do waitpid with flags <dd> (F) This machine doesn't have either waitpid() or wait4(), so only waitpid() without flags is emulated. </dd> <dt>Can't do {n,m} with n > m <dd> (F) Minima must be less than or equal to maxima. If you really want your regexp to match something 0 times, just put {0}. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Can't emulate -%s on #! line <dd> (F) The #! line specifies a switch that doesn't make sense at this point. For example, it'd be kind of silly to put a <A HREF="perlrun.html#perlrun_363">-x</A> on the #! line. </dd> <dt>Can't exec "%s": %s <dd> (W) An system(), exec() or piped open call could not execute the named program for the indicated reason. Typical reasons include: the permissions were wrong on the file, the file wasn't found in $ENV{PATH}, the executable in question was compiled for another architecture, or the #! line in a script points to an interpreter that can't be run for similar reasons. (Or maybe your system doesn't support #! at all.) </dd> <dt>Can't exec %s <dd> (F) Perl was trying to execute the indicated program for you because that's what the #! line said. If that's not what you wanted, you may need to mention "perl" on the #! line somewhere. </dd> <dt>Can't execute %s <dd> (F) You used the <A HREF="perlrun.html#perlrun_357">-S</A> switch, but the script to execute could not be found in the PATH, or at least not with the correct permissions. </dd> <dt>Can't find label %s <dd> (F) You said to goto a label that isn't mentioned anywhere that it's possible for us to go to. See perlfunc/goto. </dd> <dt>Can't find string terminator %s anywhere before EOF <dd> (F) Perl strings can stretch over multiple lines. This message means that the closing delimiter was omitted. Since bracketed quotes count nesting levels, the following is missing its final parenthesis: </dd> <pre> print q(The character '(' starts a side comment.) </pre> <dt>Can't fork <dd> (F) A fatal error occurred while trying to fork while opening a pipeline. </dd> <dt>Can't get pipe mailbox device name <dd> (F) An error peculiar to VMS. </dd> <dt>Can't get SYSGEN parameter value for MAXBUF <dd> (F) An error peculiar to VMS. </dd> <dt>Can't goto subroutine outside a subroutine <dd> (F) The deeply magical "goto subroutine" call can only replace one subroutine call for another. It can't manufacture one out of whole cloth. In general you should only be calling it out of an AUTOLOAD routine anyway. See perlfunc/goto. </dd> <dt>Can't locate %s in @INC <dd> (F) You said to do (or require, or use) a file that couldn't be found in any of the libraries mentioned in @INC. Perhaps you need to set the PERL5LIB environment variable to say where the extra library is, or maybe the script needs to add the library name to @INC. Or maybe you just misspelled the name of the file. See perlfunc/require. </dd> <dt>Can't locate object method "%s" via package "%s" <dd> (F) You called a method correctly, and it correctly indicated a package functioning as a class, but that package doesn't define that particular method, nor does any of it's base classes. See <A HREF="perlobj.html"> the perlobj manpage</A> . </dd> <dt>Can't locate package %s for @%s::ISA <dd> (W) The @ISA array contained the name of another package that doesn't seem to exist. </dd> <dt>Can't mktemp() <dd> (F) The mktemp() routine failed for some reason while trying to process a <A HREF="perlrun.html#perlrun_348">-e</A> switch. Maybe your /tmp partition is full, or clobbered. </dd> <dt>Can't modify %s in %s <dd> (F) You aren't allowed to assign to the item indicated, or otherwise try to change it, such as with an autoincrement. </dd> <dt>Can't modify non-existent substring <dd> (P) The internal routine that does assignment to a substr() was handed a NULL. </dd> <dt>Can't msgrcv to readonly var <dd> (F) The target of a msgrcv must be modifiable in order to be used as a receive buffer. </dd> <dt>Can't open %s: %s <dd> (S) An inplace edit couldn't open the original file for the indicated reason. Usually this is because you don't have read permission for the file. </dd> <dt>Can't open bidirectional pipe <dd> (W) You tried to say open(CMD, "|cmd|"), which is not supported. You can try any of several modules in the Perl library to do this, such as "open2.pl". Alternately, direct the pipe's output to a file using ">", and then read it in under a different file handle. </dd> <dt>Can't open perl script "%s": %s <dd> (F) The script you specified can't be opened for the indicated reason. </dd> <dt>Can't rename %s to %s: %s, skipping file <dd> (S) The rename done by the <A HREF="perlrun.html#perlrun_350">-i</A> switch failed for some reason, probably because you don't have write permission to the directory. </dd> <dt>Can't reswap uid and euid <dd> (P) The setreuid() call failed for some reason in the setuid emulator of suidperl. </dd> <dt>Can't return outside a subroutine <dd> (F) The return statement was executed in mainline code, that is, where there was no subroutine call to return out of. See <A HREF="perlsub.html"> the perlsub manpage</A> . </dd> <dt>Can't stat script "%s" <dd> (P) For some reason you can't fstat() the script even though you have it open already. Bizarre. </dd> <dt>Can't swap uid and euid <dd> (P) The setreuid() call failed for some reason in the setuid emulator of suidperl. </dd> <dt>Can't take log of %g <dd> (F) Logarithms are only defined on positive real numbers. </dd> <dt>Can't take sqrt of %g <dd> (F) For ordinary real numbers, you can't take the square root of a negative number. There's a Complex package available for Perl, though, if you really want to do that. </dd> <dt>Can't undef active subroutine <dd> (F) You can't undefine a routine that's currently running. You can, however, redefine it while it's running, and you can even undef the redefined subroutine while the old routine is running. Go figure. </dd> <dt>Can't unshift <dd> (F) You tried to unshift an "unreal" array that can't be unshifted, such as the main Perl stack. </dd> <dt>Can't upgrade that kind of scalar <dd> (P) The internal sv_upgrade routine adds "members" to an SV, making it into a more specialized kind of SV. The top several SV types are so specialized, however, that they cannot be interconverted. This message indicates that such a conversion was attempted. </dd> <dt>Can't upgrade to undef <dd> (P) The undefined SV is the bottom of the totem pole, in the scheme of upgradability. Upgrading to undef indicates an error in the code calling sv_upgrade. </dd> <dt>Can't use %s as left arg of an implicit -> <dd> (F) The compiler tried to interpret a bracketed expression as a subscript to an array reference. But to the left of the brackets was an expression that didn't end in an arrow (->), or look like a subscripted expression. Only subscripted expressions with multiple subscripts are allowed to omit the intervening arrow. </dd> <dt>Can't use %s for loop variable <dd> (F) Only a simple scalar variable may be used as a loop variable on a foreach. </dd> <dt>Can't use %s ref as %s ref <dd> (F) You've mixed up your reference types. You have to dereference a reference of the type needed. You can use the ref() function to test the type of the reference, if need be. </dd> <dt>Can't use a string as %s ref while "strict refs" in use <dd> (F) Only hard references are allowed by "strict refs". Symbolic references are disallowed. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Can't use an undefined value as %s reference <dd> (F) A value used as either a hard reference or a symbolic reference must be a defined value. This helps to de-lurk some insidious errors. </dd> <dt>Can't use delimiter brackets within expression <dd> (F) The ${name} construct is for disambiguating identifiers in strings, not in ordinary code. </dd> <dt>Can't use global %s in "my" <dd> (F) You tried to declare a magical variable as a lexical variable. This is not allowed, because the magic can only be tied to one location (namely the global variable) and it would be incredibly confusing to have variables in your program that looked like magical variables but weren't. </dd> <dt>Can't write to temp file for <A HREF="perlrun.html#perlrun_348">-e</A> : %s <dd> (F) The write routine failed for some reason while trying to process a <A HREF="perlrun.html#perlrun_348">-e</A> switch. Maybe your /tmp partition is full, or clobbered. </dd> <dt>Can't x= to readonly value <dd> (F) You tried to repeat a constant value (often the undefined value) with an assignment operator, which implies modifying the value itself. Perhaps you need to copy the value to a temporary, and repeat that. </dd> <dt>Cannot open temporary file <dd> (F) The create routine failed for some reaon while trying to process a <A HREF="perlrun.html#perlrun_348">-e</A> switch. Maybe your /tmp partition is full, or clobbered. </dd> <dt>chmod: mode argument is missing initial 0 <dd> (W) A novice will sometimes say </dd> <pre> chmod 777, $filename </pre> not realizing that 777 will be interpreted as a decimal number, equivalent to 01411. Octal constants are introduced with a leading 0 in Perl, as in C. <dt>Close on unopened file <%s> <dd> (W) You tried to close a filehandle that was never opened. </dd> <dt>connect() on closed fd <dd> (W) You tried to do a connect on a closed socket. Did you forget to check the return value of your socket() call? See perlfunc/connect. </dd> <dt>Corrupt malloc ptr 0x%lx at 0x%lx <dd> (P) The malloc package that comes with Perl had an internal failure. </dd> <dt>corrupted regexp pointers <dd> (P) The regular expression engine got confused by what the regular expression compiler gave it. </dd> <dt>corrupted regexp program <dd> (P) The regular expression engine got passed a regexp program without a valid magic number. </dd> <dt>Deep recursion on subroutine "%s" <dd> (W) This subroutine has called itself (directly or indirectly) 100 times than it has returned. This probably indicates an infinite recursion, unless you're writing strange benchmark programs, in which case it indicates something else. </dd> <dt>Did you mean $ instead of %? <dd> (W) You probably said %hash{$key} when you meant $hash{$key}. </dd> <dt>Don't know how to handle magic of type '%s' <dd> (P) The internal handling of magical variables has been cursed. </dd> <dt>do_study: out of memory <dd> (P) This should have been caught by safemalloc() instead. </dd> <dt>Duplicate free() ignored <dd> (S) An internal routine called free() on something that had already been freed. </dd> <dt>END failed--cleanup aborted <dd> (F) An untrapped exception was raised while executing an END subroutine. The interpreter is immediately exited. </dd> <dt>Execution of %s aborted due to compilation errors. <dd> (F) The final summary message when a Perl compilation fails. </dd> <dt>Exiting eval via %s <dd> (W) You are exiting an eval by unconventional means, such as a a goto, or a loop control statement. </dd> <dt>Exiting subroutine via %s <dd> (W) You are exiting a subroutine by unconventional means, such as a a goto, or a loop control statement. </dd> <dt>Exiting substitution via %s <dd> (W) You are exiting a substitution by unconventional means, such as a a return, a goto, or a loop control statement. </dd> <dt>Fatal $PUTMSG error: %d <dd> (F) An error peculiar to VMS. </dd> <dt><A NAME="perlfunc_106">fcntl is not implemented</A> <dd> (F) Your machine apparently doesn't implement fcntl(). What is this, a PDP-11 or something? </dd> <dt>Filehandle %s never opened <dd> (W) An I/O operation was attempted on a filehandle that was never initialized. You need to do an open() or a socket() call, or call a constructor from the FileHandle package. </dd> <dt>Filehandle %s opened only for input <dd> (W) You tried to write on a read-only filehandle. If you intended it to be a read-write filehandle, you needed to open it with "+<" or "+>" or ">>" instead of with "<" or nothing. If you only intended to write the file, use ">" or >>". See perlfunc/open. </dd> <dt>Filehandle only opened for input <dd> (W) You tried to write on a read-only filehandle. If you intended it to be a read-write filehandle, you needed to open it with "+<" or "+>" or ">>" instead of with "<" or nothing. If you only intended to write the file, use ">" or >>". See perlfunc/open. </dd> <dt>Final $ should be \$ or $name <dd> (F) You must now decide whether the final $ in a string was meant to be a literal dollar sign, or was meant to introduce a variable name that happens to be missing. So you have to put either the backslash or the name. </dd> <dt>Final @ should be \@ or @name <dd> (F) You must now decide whether the final @ in a string was meant to be a literal "at" sign, or was meant to introduce a variable name that happens to be missing. So you have to put either the backslash or the name. </dd> <dt>Format %s redefined <dd> (W) You redefined a format. To suppress this warning, say </dd> <pre> { local $^W = 0; eval "format NAME =..."; } </pre> <dt>Format not terminated <dd> (F) A format must be terminated by a line with a solitary dot. Perl got to the end of your file without finding such a line. </dd> <dt>Found = in conditional, should be == <dd> (W) You said </dd> <pre> if ($foo = 123) </pre> when you meant <pre> if ($foo == 123) </pre> (or something like that). <dt>gdbm store returned %d, errno %d, key "%s" <dd> (S) A warning from the GDBM_File extension that a store failed. </dd> <dt><A NAME="perlfunc_131">gethostent not implemented</A> <dd> (F) Your C library apparently doesn't implement gethostent(), probably because if it did, it'd feel morally obligated to return every hostname on the Internet. </dd> <dt>get{sock,peer}name() on closed fd <dd> (W) You tried to get a socket or peer socket name on a closed socket. Did you forget to check the return value of your socket() call? </dd> <dt>Glob not terminated <dd> (F) The lexer saw a left angle bracket in a place where it was expecting a term, so it's looking for the corresponding right angle bracket, and not finding it. Chances are you left some needed parentheses out earlier in the line, and you really meant a "less than". </dd> <dt>Global symbol "%s" requires explicit package name <dd> (F) You've said "use strict vars", which indicates that all variables must either be lexically scoped (using "my"), or explicitly qualified to say which package the global variable is in (using "::"). </dd> <dt><A NAME="perlfunc_151">goto must have label</A> <dd> (F) Unlike with "next" or "last", you're not allowed to goto an unspecified destination. See perlfunc/goto. </dd> <dt>Had to create %s unexpectedly <dd> (S) A routine asked for a symbol from a symbol table that ought to have existed already, but for some reason it didn't, and had to be created on an emergency basis to prevent a core dump. </dd> <dt>Hash %%s missing the % in argument %d of %s() <dd> (D) Really old Perl let you omit the % on hash names in some spots. This is now heavily deprecated. </dd> <dt>Identifier "%s::%s" used only once: possible typo <dd> (W) Typographical errors often show up as unique identifiers. If you had a good reason for having a unique identifier, then just mention it again somehow to suppress the message. </dd> <dt>Illegal division by zero <dd> (F) You tried to divide a number by 0. Either something was wrong in your logic, or you need to put a conditional in to guard against meaningless input. </dd> <dt>Illegal modulus zero <dd> (F) You tried to divide a number by 0 to get the remainder. Most numbers don't take to this kindly. </dd> <dt>Illegal octal digit <dd> (F) You used an 8 or 9 in a octal number. </dd> <dt>Insecure dependency in %s <dd> (F) You tried to do something that the tainting mechanism didn't like. The tainting mechanism is turned on when you're running setuid or setgid, or when you specify <A HREF="perlrun.html#perlrun_358">-T</A> to turn it on explicitly. The tainting mechanism labels all data that's derived directly or indirectly from the user, who is considered to be unworthy of your trust. If any such data is used in a "dangerous" operation, you get this error. See <A HREF="perlsec.html"> the perlsec manpage</A> for more information. </dd> <dt>Insecure directory in %s <dd> (F) You can't use system(), exec(), or a piped open in a setuid or setgid script if $ENV{PATH} contains a directory that is writable by the world. See <A HREF="perlsec.html"> the perlsec manpage</A> . </dd> <dt>Insecure PATH <dd> (F) You can't use system(), exec(), or a piped open in a setuid or setgid script if $ENV{PATH} is derived from data supplied (or potentially supplied) by the user. The script must set the path to a known value, using trustworthy data. See <A HREF="perlsec.html"> the perlsec manpage</A> . </dd> <dt>internal disaster in regexp <dd> (P) Something went badly wrong in the regular expression parser. </dd> <dt>internal urp in regexp at /%s/ <dd> (P) Something went badly awry in the regular expression parser. </dd> <dt>invalid [] range in regexp <dd> (F) The range specified in a character class had a minimum character greater than the maximum character. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt><A NAME="perlfunc_157">ioctl is not implemented</A> <dd> (F) Your machine apparently doesn't implement ioctl(), which is pretty strange for a machine that supports C. </dd> <dt>junk on end of regexp <dd> (P) The regular expression parser is confused. </dd> <dt>Label not found for "last %s" <dd> (F) You named a loop to break out of, but you're not currently in a loop of that name, not even if you count where you were called from. See perlfunc/last. </dd> <dt>Label not found for "next %s" <dd> (F) You named a loop to continue, but you're not currently in a loop of that name, not even if you count where you were called from. See perlfunc/last. </dd> <dt>Label not found for "redo %s" <dd> (F) You named a loop to restart, but you're not currently in a loop of that name, not even if you count where you were called from. See perlfunc/last. </dd> <dt>listen() on closed fd <dd> (W) You tried to do a listen on a closed socket. Did you forget to check the return value of your socket() call? See perlfunc/listen. </dd> <dt>Literal @%s now requires backslash <dd> (F) It used to be that Perl would try to guess whether you wanted an array interpolated or a literal @. It did this when the string was first used at runtime. Now strings are parsed at compile time, and ambiguous instances of @ must be disambiguated, either by putting a backslash to indicate a literal, or by declaring (or using) the array within the program before the string (lexically). (Someday it will simply assume that an unbackslashed @ interpolates an array.) </dd> <dt>Method for operation %s not found in package %s during blessing <dd> (F) An attempt was made to specify an entry in an overloading table that doesn't somehow point to a valid method. See <A HREF="perlovl.html"> the perlovl manpage</A> . </dd> <dt>Might be a runaway multi-line %s string starting on line %d <dd> (S) An advisory indicating that the previous error may have been caused by a missing delimiter on a string or pattern, because it eventually ended earlier on the current line. </dd> <dt>Misplaced _ in number <dd> (W) An underline in a decimal constant wasn't on a 3-digit boundary. </dd> <dt>Missing $ on loop variable <dd> (F) Apparently you've been programming in csh too much. Variables are always mentioned with the $ in Perl, unlike in the shells, where it can vary from one line to the next. </dd> <dt>Missing comma after first argument to %s function <dd> (F) While certain functions allow you to specify a filehandle or an "indirect object" before the argument list, this ain't one of them. </dd> <dt>Missing right bracket <dd> (F) The lexer counted more opening curly brackets (braces) than closing ones. As a general rule, you'll find it's missing near the place you were last editing. </dd> <dt>Missing semicolon on previous line? <dd> (S) This is an educated guess made in conjunction with the message "%s found where operator expected". Don't automatically put a semicolon on the previous line just because you saw this message. </dd> <dt>Modification of a read-only value attempted <dd> (F) You tried, directly or indirectly, to change the value of a constant. You didn't, of course, try "2 = 1", since the compiler catches that. But an easy way to do the same thing is: </dd> <pre> sub mod { $_[0] = 1 } mod(2); </pre> Another way is to assign to a substr() that's off the end of the string. <dt>Modification of non-creatable array value attempted, subscript %d <dd> (F) You tried to make an array value spring into existence, and the subscript was probably negative, even counting from end of the array backwards. </dd> <dt>Modification of non-creatable hash value attempted, subscript "%s" <dd> (F) You tried to make a hash value spring into existence, and it couldn't be created for some peculiar reason. </dd> <dt>Module name must be constant <dd> (F) Only a bare module name is allowed as the first argument to a "use". </dd> <dt>msg%s not implemented <dd> (F) You don't have System V message IPC on your system. </dd> <dt>Multidimensional syntax %s not supported <dd> (W) Multidimensional arrays aren't written like $foo[1,2,3]. They're written like $foo[1][2][3], as in C. </dd> <dt>Negative length <dd> (F) You tried to do a read/write/send/recv operation with a buffer length that is less than 0. This is difficult to imagine. </dd> <dt>nested *?+ in regexp <dd> (F) You can't quantify a quantifier without intervening parens. So things like ** or +* or ?* are illegal. </dd> Note, however, that the minimal matching quantifiers, *?, +? and ?? appear to be nested quantifiers, but aren't. See <A HREF="perlre.html"> the perlre manpage</A> . <dt>No #! line <dd> (F) The setuid emulator requires that scripts have a well-formed #! line even on machines that don't support the #! construct. </dd> <dt>No %s allowed while running setuid <dd> (F) Certain operations are deemed to be too insecure for a setuid or setgid script to even be allowed to attempt. Generally speaking there will be another way to do what you want that is, if not secure, at least securable. See <A HREF="perlsec.html"> the perlsec manpage</A> . </dd> <dt>No <A HREF="perlrun.html#perlrun_348">-e</A> allowed in setuid scripts <dd> (F) A setuid script can't be specified by the user. </dd> <dt>No comma allowed after %s <dd> (F) A list operator that has a filehandle or "indirect object" is not allowed to have a comma between that and the following arguments. Otherwise it'd be just another one of the arguments. </dd> <dt>No DB::DB routine defined <dd> (F) The currently executing code was compiled with the <A HREF="perlrun.html#perlrun_346">-d</A> switch, but for some reason the perl5db.pl file (or some facsimile thereof) didn't define a routine to be called at the beginning of each statement. Which is odd, because the file should have been required automatically, and should have blown up the require if it didn't parse right. </dd> <dt>No dbm on this machine <dd> (P) This is counted as an internal error, because every machine should supply dbm nowadays, since Perl comes with SDBM. See SDBM_File. </dd> <dt>No DBsub routine <dd> (F) The currently executing code was compiled with the <A HREF="perlrun.html#perlrun_346">-d</A> switch, but for some reason the perl5db.pl file (or some facsimile thereof) didn't define a DB::sub routine to be called at the beginning of each ordinary subroutine call. </dd> <dt>No Perl script found in input <dd> (F) You called perl -x, but no line was found in the file beginning with #! and containing the word "perl". </dd> <dt>No setregid available <dd> (F) Configure didn't find anything resembling the setregid() call for your system. </dd> <dt>No setreuid available <dd> (F) Configure didn't find anything resembling the setreuid() call for your system. </dd> <dt>No space allowed after <A HREF="perlrun.html#perlrun_351">-I</A> <dd> (F) The argument to <A HREF="perlrun.html#perlrun_351">-I</A> must follow the <A HREF="perlrun.html#perlrun_351">-I</A> immediately with no intervening space. </dd> <dt>No such signal: SIG%s <dd> (W) You specified a signal name as a subscript to %SIG that was not recognized. Say kill -l in your shell to see the valid signal names on your system. </dd> <dt>Not a CODE reference <dd> (F) Perl was trying to evaluate a reference to a code value (that is, a subroutine), but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See also <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not a format reference <dd> (F) I'm not sure how you managed to generate a reference to an anonymous format, but this indicates you did, and that it didn't exist. </dd> <dt>Not a GLOB reference <dd> (F) Perl was trying to evaluate a reference to a "type glob" (that is, a symbol table entry that looks like *foo), but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not a HASH reference <dd> (F) Perl was trying to evaluate a reference to a hash value, but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not a perl script <dd> (F) The setuid emulator requires that scripts have a well-formed #! line even on machines that don't support the #! construct. The line must mention perl. </dd> <dt>Not a SCALAR reference <dd> (F) Perl was trying to evaluate a reference to a scalar value, but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not a subroutine reference <dd> (F) Perl was trying to evaluate a reference to a code value (that is, a subroutine), but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See also <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not a subroutine reference in %OVERLOAD <dd> (F) An attempt was made to specify an entry in an overloading table that doesn't somehow point to a valid subroutine. See <A HREF="perlovl.html"> the perlovl manpage</A> . </dd> <dt>Not an ARRAY reference <dd> (F) Perl was trying to evaluate a reference to an array value, but found a reference to something else instead. You can use the ref() function to find out what kind of ref it really was. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>Not enough arguments for %s <dd> (F) The function requires more arguments than you specified. </dd> <dt>Not enough format arguments <dd> (W) A format specified more picture fields than the next line supplied. See <A HREF="perlform.html"> the perlform manpage</A> . </dd> <dt>Null filename used <dd> (F) You can't require the null filename, especially since on many machines that means the current directory! See perlfunc/require. </dd> <dt>NULL OP IN RUN <dd> (P) Some internal routine called run() with a null opcode pointer. </dd> <dt>Null realloc <dd> (P) An attempt was made to realloc NULL. </dd> <dt>NULL regexp argument <dd> (P) The internal pattern matching routines blew it bigtime. </dd> <dt>NULL regexp parameter <dd> (P) The internal pattern matching routines are out of their gourd. </dd> <dt>Odd number of elements in hash list <dd> (S) You specified an odd number of elements to a hash list, which is odd, since hash lists come in key/value pairs. </dd> <dt>oops: oopsAV <dd> (S) An internal warning that the grammar is screwed up. </dd> <dt>oops: oopsHV <dd> (S) An internal warning that the grammar is screwed up. </dd> <dt>Operation `%s' %s: no method found, <dd> (F) An attempt was made to use an entry in an overloading table that somehow no longer points to a valid method. See <A HREF="perlovl.html"> the perlovl manpage</A> . </dd> <dt>Out of memory for yacc stack <dd> (F) The yacc parser wanted to grow its stack so it could continue parsing, but realloc() wouldn't give it more memory, virtual or otherwise. </dd> <dt>Out of memory! <dd> (X) The malloc() function returned 0, indicating there was insufficient remaining memory (or virtual memory) to satisfy the request. </dd> <dt>page overflow <dd> (W) A single call to write() produced more lines than can fit on a page. See <A HREF="perlform.html"> the perlform manpage</A> . </dd> <dt>panic: ck_grep <dd> (P) Failed an internal consistency check trying to compile a grep. </dd> <dt>panic: ck_split <dd> (P) Failed an internal consistency check trying to compile a split. </dd> <dt>panic: corrupt saved stack index <dd> (P) The savestack was requested to restore more localized values than there are in the savestack. </dd> <dt>panic: die %s <dd> (P) We popped the context stack to an eval context, and then discovered it wasn't an eval context. </dd> <dt>panic: do_match <dd> (P) The internal pp_match() routine was called with invalid operational data. </dd> <dt>panic: do_split <dd> (P) Something terrible went wrong in setting up for the split. </dd> <dt>panic: do_subst <dd> (P) The internal pp_subst() routine was called with invalid operational data. </dd> <dt>panic: do_trans <dd> (P) The internal do_trans() routine was called with invalid operational data. </dd> <dt>panic: goto <dd> (P) We popped the context stack to a context with the specified label, and then discovered it wasn't a context we know how to do a goto in. </dd> <dt>panic: INTERPCASEMOD <dd> (P) The lexer got into a bad state at a case modifier. </dd> <dt>panic: INTERPCONCAT <dd> (P) The lexer got into a bad state parsing a string with brackets. </dd> <dt>panic: last <dd> (P) We popped the context stack to a block context, and then discovered it wasn't a block context. </dd> <dt>panic: leave_scope clearsv <dd> (P) A writable lexical variable became readonly somehow within the scope. </dd> <dt>panic: leave_scope inconsistency <dd> (P) The savestack probably got out of sync. At least, there was an invalid enum on the top of it. </dd> <dt>panic: malloc <dd> (P) Something requested a negative number of bytes of malloc. </dd> <dt>panic: mapstart <dd> (P) The compiler is screwed up with respect to the map() function. </dd> <dt>panic: null array <dd> (P) One of the internal array routines was passed a null AV pointer. </dd> <dt>panic: pad_alloc <dd> (P) The compiler got confused about which scratch pad it was allocating and freeing temporaries and lexicals from. </dd> <dt>panic: pad_free curpad <dd> (P) The compiler got confused about which scratch pad it was allocating and freeing temporaries and lexicals from. </dd> <dt>panic: pad_free po <dd> (P) An invalid scratch pad offset was detected internally. </dd> <dt>panic: pad_reset curpad <dd> (P) The compiler got confused about which scratch pad it was allocating and freeing temporaries and lexicals from. </dd> <dt>panic: pad_sv po <dd> (P) An invalid scratch pad offset was detected internally. </dd> <dt>panic: pad_swipe curpad <dd> (P) The compiler got confused about which scratch pad it was allocating and freeing temporaries and lexicals from. </dd> <dt>panic: pad_swipe po <dd> (P) An invalid scratch pad offset was detected internally. </dd> <dt>panic: pp_iter <dd> (P) The foreach iterator got called in a non-loop context frame. </dd> <dt>panic: realloc <dd> (P) Something requested a negative number of bytes of realloc. </dd> <dt>panic: restartop <dd> (P) Some internal routine requested a goto (or something like it), and didn't supply the destination. </dd> <dt>panic: return <dd> (P) We popped the context stack to a subroutine or eval context, and then discovered it wasn't a subroutine or eval context. </dd> <dt>panic: scan_num <dd> (P) scan_num() got called on something that wasn't a number. </dd> <dt>panic: sv_insert <dd> (P) The sv_insert() routine was told to remove more string than there was string. </dd> <dt>panic: top_env <dd> (P) The compiler attempted to do a goto, or something weird like that. </dd> <dt>panic: yylex <dd> (P) The lexer got into a bad state while processing a case modifier. </dd> <dt>Parens missing around "%s" list <dd> (W) You said something like </dd> <pre> my $foo, $bar = @_; </pre> when you meant <pre> my ($foo, $bar) = @_; </pre> Remember that "my" and "local" bind closer than comma. <dt>Perl %3.3f required--this is only version %s, stopped <dd> (F) The module in question uses features of a version of Perl more recent than the currently running version. How long has it been since you upgraded, anyway? See perlfunc/require. </dd> <dt>Permission denied <dd> (F) The setuid emulator in suidperl decided you were up to no good. </dd> <dt>POSIX getpgrp can't take an argument <dd> (F) Your C compiler uses POSIX getpgrp(), which takes no argument, unlike the BSD version, which takes a pid. </dd> <dt>Possible memory corruption: %s overflowed 3rd argument <dd> (F) An ioctl() or fcntl() returned more than Perl was bargaining for. Perl guesses a reasonable buffer size, but puts a sentinel byte at the end of the buffer just in case. This sentinel byte got clobbered, and Perl assumes that memory is now corrupted. See perlfunc/ioctl. </dd> <dt>Precedence problem: open %s should be open(%s) <dd> (S) The old irregular construct open FOO || die; </dd> is now misinterpreted as <pre> open(FOO || die); </pre> because of the strict regularization of Perl 5's grammar into unary and list operators. (The old open was a little of both.) You must put parens around the filehandle, or use the new "or" operator instead of "||". <dt><A NAME="perlfunc_189">print on closed filehandle %s</A> <dd> (W) The filehandle you're printing on got itself closed sometime before now. Check your logic flow. </dd> <dt><A NAME="perlfunc_190">printf on closed filehandle %s</A> <dd> (W) The filehandle you're writing to got itself closed sometime before now. Check your logic flow. </dd> <dt>Probable precedence problem on %s <dd> (W) The compiler found a bare word where it expected a conditional, which often indicates that an || or && was parsed as part of the last argument of the previous construct, for example: </dd> <pre> open FOO || die; </pre> <dt>Read on closed filehandle <%s> <dd> (W) The filehandle you're reading from got itself closed sometime before now. Check your logic flow. </dd> <dt>Reallocation too large: %lx <dd> (F) You can't allocate more than 64K on an MSDOS machine. </dd> <dt>Recompile perl with <A HREF="perlrun.html#perlrun_347">-D</A> DEBUGGING to use <A HREF="perlrun.html#perlrun_347">-D</A> switch <dd> (F) You can't use the <A HREF="perlrun.html#perlrun_347">-D</A> option unless the code to produce the desired output is compiled into Perl, which entails some overhead, which is why it's currently left out of your copy. </dd> <dt>Recursive inheritance detected <dd> (F) More than 100 levels of inheritance were used. Probably indicates an unintended loop in your inheritance hierarchy. </dd> <dt>Reference miscount in sv_replace() <dd> (W) The internal sv_replace() function was handed a new SV with a reference count of other than 1. </dd> <dt>regexp memory corruption <dd> (P) The regular expression engine got confused by what the regular expression compiler gave it. </dd> <dt>regexp out of space <dd> (P) A "can't happen" error, because safemalloc() should have caught it earlier. </dd> <dt>regexp too big <dd> (F) The current implementation of regular expression uses shorts as address offsets within a string. Unfortunately this means that if the regular expression compiles to longer than 32767, it'll blow up. Usually when you want a regular expression this big, there is a better way to do it with multiple statements. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Reversed %s= operator <dd> (W) You wrote your assignment operator backwards. The = must always comes last, to avoid ambiguity with subsequent unary operators. </dd> <dt>Runaway format <dd> (F) Your format contained the ~~ repeat-until-blank sequence, but it produced 200 lines at once, and the 200th line looked exactly like the 199th line. Apparently you didn't arrange for the arguments to exhaust themselves, either by using ^ instead of @ (for scalar variables), or by shifting or popping (for array variables). See <A HREF="perlform.html"> the perlform manpage</A> . </dd> <dt>Scalar value @%s[%s] better written as $%s[%s] <dd> (W) You've used an array slice (indicated by @) to select a single value of an array. Generally it's better to ask for a scalar value (indicated by $). The difference is that $foo[&bar] always behaves like a scalar, both when assigning to it and when evaluating its argument, while @foo[&bar] behaves like a list when you assign to it, and provides a list context to its subscript, which can do weird things if you're only expecting one subscript. </dd> <dt>Script is not setuid/setgid in suidperl <dd> (F) Oddly, the suidperl program was invoked on a script with its setuid or setgid bit set. This doesn't make much sense. </dd> <dt>Search pattern not terminated <dd> (F) The lexer couldn't find the final delimiter of a // or m{} construct. Remember that bracketing delimiters count nesting level. </dd> <dt>seek() on unopened file <dd> (W) You tried to use the seek() function on a filehandle that was either never opened or has been closed since. </dd> <dt><A NAME="perlfunc_216">select not implemented</A> <dd> (F) This machine doesn't implement the select() system call. </dd> <dt>sem%s not implemented <dd> (F) You don't have System V semaphore IPC on your system. </dd> <dt>semi-panic: attempt to dup freed string <dd> (S) The internal newSVsv() routine was called to duplicate a scalar that had previously been marked as free. </dd> <dt>Semicolon seems to be missing <dd> (W) A nearby syntax error was probably caused by a missing semicolon, or possibly some other missing operator, such as a comma. </dd> <dt>Send on closed socket <dd> (W) The filehandle you're sending to got itself closed sometime before now. Check your logic flow. </dd> <dt>Sequence (?#... not terminated <dd> (F) A regular expression comment must be terminated by a closing parenthesis. Embedded parens aren't allowed. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Sequence (?%s...) not implemented <dd> (F) A proposed regular expression extension has the character reserved but has not yet been written. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Sequence (?%s...) not recognized <dd> (F) You used a regular expression extension that doesn't make sense. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>setegid() not implemented <dd> (F) You tried to assign to $), and your operating system doesn't support the setegid() system call (or equivalent), or at least Configure didn't think so. </dd> <dt>seteuid() not implemented <dd> (F) You tried to assign to $>, and your operating system doesn't support the seteuid() system call (or equivalent), or at least Configure didn't think so. </dd> <dt>setrgid() not implemented <dd> (F) You tried to assign to $(, and your operating system doesn't support the setrgid() system call (or equivalent), or at least Configure didn't think so. </dd> <dt>setruid() not implemented <dd> (F) You tried to assign to $<, and your operating system doesn't support the setruid() system call (or equivalent), or at least Configure didn't think so. </dd> <dt>Setuid/gid script is writable by world <dd> (F) The setuid emulator won't run a script that is writable by the world, because the world might have written on it already. </dd> <dt>shm%s not implemented <dd> (F) You don't have System V shared memory IPC on your system. </dd> <dt>shutdown() on closed fd <dd> (W) You tried to do a shutdown on a closed socket. Seems a bit superfluous. </dd> <dt>SIG%s handler "%s" not defined. <dd> (W) The signal handler named in %SIG doesn't, in fact, exist. Perhaps you put it into the wrong package? </dd> <dt><A NAME="perlfunc_234">sort is now a reserved word</A> <dd> (F) An ancient error message that almost nobody ever runs into anymore. But before sort was a keyword, people sometimes used it as a filehandle. </dd> <dt>Sort subroutine didn't return a numeric value <dd> (F) A sort comparison routine must return a number. You probably blew it by not using C<<=> or cmp, or by not using them correctly. See perlfunc/sort. </dd> <dt>Sort subroutine didn't return single value <dd> (F) A sort comparison subroutine may not return a list value with more or less than one element. See perlfunc/sort. </dd> <dt>Split loop <dd> (P) The split was looping infinitely. (Obviously, a split shouldn't iterate more times than there are characters of input, which is what happened.) See perlfunc/split. </dd> <dt>Stat on unopened file <%s> <dd> (W) You tried to use the stat() function (or an equivalent file test) on a filehandle that was either never opened or has been closed since. </dd> <dt>Statement unlikely to be reached <dd> (W) You did an exec() with some statement after it other than a die(). This is almost always an error, because exec() never returns unless there was a failure. You probably wanted to use system() instead, which does return. To suppress this warning, put the exec() in a block by itself. </dd> <dt>Subroutine %s redefined <dd> (W) You redefined a subroutine. To suppress this warning, say </dd> <pre> { local $^W = 0; eval "sub name { ... }"; } </pre> <dt>Substitution loop <dd> (P) The substitution was looping infinitely. (Obviously, a substitution shouldn't iterate more times than there are characters of input, which is what happened.) See the discussion of substitution in perlop/"Quote and Quotelike Operators". </dd> <dt>Substitution pattern not terminated <dd> (F) The lexer couldn't find the interior delimiter of a s/// or s{}{} construct. Remember that bracketing delimiters count nesting level. </dd> <dt>Substitution replacement not terminated <dd> (F) The lexer couldn't find the final delimiter of a s/// or s{}{} construct. Remember that bracketing delimiters count nesting level. </dd> <dt><A NAME="perlfunc_242">substr outside of string</A> <dd> (W) You tried to reference a substr() that pointed outside of a string. That is, the absolute value of the offset was larger than the length of the string. See perlfunc/substr. </dd> <dt>suidperl is no longer needed since... <dd> (F) Your Perl was compiled with <A HREF="perlrun.html#perlrun_347">-D</A> SETUID_SCRIPTS_ARE_SECURE_NOW, but a version of the setuid emulator somehow got run anyway. </dd> <dt>syntax error <dd> (F) Probably means you had a syntax error. Common reasons include: </dd> <pre> A keyword is misspelled. A semicolon is missing. A comma is missing. An opening or closing parenthesis is missing. An opening or closing brace is missing. A closing quote is missing. </pre> Often there will be another error message associated with the syntax error giving more information. (Sometimes it helps to turn on <A HREF="perlrun.html#perlrun_362">-w</A> .) The error message itself often tells you where it was in the line when it decided to give up. Sometimes the actual error is several tokens before this, since Perl is good at understanding random input. Occasionally the line number may be misleading, and once in a blue moon the only way to figure out what's triggering the error is to call perl -c repeatedly, chopping away half the program each time to see if the error went away. Sort of the cybernetic version of 20 questions. <dt>System V IPC is not implemented on this machine <dd> (F) You tried to do something with a function beginning with "sem", "shm" or "msg". See perlfunc/semctl, for example. </dd> <dt>Syswrite on closed filehandle <dd> (W) The filehandle you're writing to got itself closed sometime before now. Check your logic flow. </dd> <dt>tell() on unopened file <dd> (W) You tried to use the tell() function on a filehandle that was either never opened or has been closed since. </dd> <dt>Test on unopened file <%s> <dd> (W) You tried to invoke a file test operator on a filehandle that isn't open. Check your logic. See also perlfunc/-X. </dd> <dt>That use of $[ is unsupported <dd> (F) Assignment to $[ is now strictly circumscribed, and interpreted as a compiler directive. You may only say one of </dd> <pre> $[ = 0; $[ = 1; ... local $[ = 0; local $[ = 1; ... </pre> This is to prevent the problem of one module changing the array base out from under another module inadvertently. See perlvar/$[. <dt>The %s function is unimplemented <dd> The function indicated isn't implemented on this architecture, according to the probings of Configure. </dd> <dt>The crypt() function is unimplemented due to excessive paranoia. <dd> (F) Configure couldn't find the crypt() function on your machine, probably because your vendor didn't supply it, probably because they think the U.S. Govermnment thinks it's a secret, or at least that they will continue to pretend that it is. And if you quote me on that, I will deny it. </dd> <dt>The stat preceding -l _ wasn't an lstat <dd> (F) It makes no sense to test the current stat buffer for symbolic linkhood if the last stat that wrote to the stat buffer already went past the symlink to get to the real file. Use an actual filename instead. </dd> <dt><A NAME="perlfunc_252">times not implemented</A> <dd> (F) Your version of the C library apparently doesn't do times(). I suspect you're not running on Unix. </dd> <dt>Too few args to syscall <dd> (F) There has to be at least one argument to syscall() to specify the system call to call, silly dilly. </dd> <dt>Too many args to syscall <dd> (F) Perl only supports a maximum of 14 args to syscall(). </dd> <dt>Too many arguments for %s <dd> (F) The function requires fewer arguments than you specified. </dd> <dt>trailing \ in regexp <dd> (F) The regular expression ends with an unbackslashed backslash. Backslash it. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Translation pattern not terminated <dd> (F) The lexer couldn't find the interior delimiter of a tr/// or tr[][] construct. </dd> <dt>Translation replacement not terminated <dd> (F) The lexer couldn't find the final delimiter of a tr/// or tr[][] construct. </dd> <dt><A NAME="perlfunc_254">truncate not implemented</A> <dd> (F) Your machine doesn't implement a file truncation mechanism that Configure knows about. </dd> <dt>Type of arg %d to %s must be %s (not %s) <dd> (F) This function requires the argument in that position to be of a certain type. Arrays must be @NAME or @{EXPR}. Hashes must be %NAME or %{EXPR}. No implicit dereferencing is allowed--use the {EXPR} forms as an explicit dereference. See <A HREF="perlref.html"> the perlref manpage</A> . </dd> <dt>umask: argument is missing initial 0 <dd> (W) A umask of 222 is incorrect. It should be 0222, since octal literals always start with 0 in Perl, as in C. </dd> <dt>Unbalanced context: %d more PUSHes than POPs <dd> (W) The exit code detected an internal inconsistency in how many execution contexts were entered and left. </dd> <dt>Unbalanced saves: %d more saves than restores <dd> (W) The exit code detected an internal inconsistency in how many values were temporarily localized. </dd> <dt>Unbalanced scopes: %d more ENTERs than LEAVEs <dd> (W) The exit code detected an internal inconsistency in how many blocks were entered and left. </dd> <dt>Unbalanced tmps: %d more allocs than frees <dd> (W) The exit code detected an internal inconsistency in how many mortal scalars were allocated and freed. </dd> <dt>Undefined format "%s" called <dd> (F) The format indicated doesn't seem to exist. Perhaps it's really in another package? See <A HREF="perlform.html"> the perlform manpage</A> . </dd> <dt>Undefined sort subroutine "%s" called <dd> (F) The sort comparison routine specified doesn't seem to exist. Perhaps it's in a different package? See perlfunc/sort. </dd> <dt>Undefined subroutine &%s called <dd> (F) The subroutine indicated hasn't been defined, or if it was, it has since been undefined. </dd> <dt>Undefined subroutine called <dd> (F) The anonymous subroutine you're trying to call hasn't been defined, or if it was, it has since been undefined. </dd> <dt>Undefined subroutine in sort <dd> (F) The sort comparison routine specified is declared but doesn't seem to have been defined yet. See perlfunc/sort. </dd> <dt>unexec of %s into %s failed! <dd> (F) The unexec() routine failed for some reason. See your local FSF representative, who probably put it there in the first place. </dd> <dt>Unknown BYTEORDER <dd> (F) There are no byteswapping functions for a machine with this byte order. </dd> <dt>unmatched () in regexp <dd> (F) Unbackslashed parentheses must always be balanced in regular expressions. If you're a vi user, the % key is valuable for finding the matching paren. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Unmatched right bracket <dd> (F) The lexer counted more closing curly brackets (braces) than opening ones, so you're probably missing an opening bracket. As a general rule, you'll find the missing one (so to speak) near the place you were last editing. </dd> <dt>unmatched [] in regexp <dd> (F) The brackets around a character class must match. If you wish to include a closing bracket in a character class, backslash it or put it first. See <A HREF="perlre.html"> the perlre manpage</A> . </dd> <dt>Unquoted string "%s" may clash with future reserved word <dd> (W) You used a bare word that might someday be claimed as a reserved word. It's best to put such a word in quotes, or capitalize it somehow, or insert an underbar into it. You might also declare it as a subroutine. </dd> <dt>Unrecognized character \%03o ignored <dd> (S) A garbage character was found in the input, and ignored, in case it's a weird control character on an EBCDIC machine, or some such. </dd> <dt>Unrecognized signal name "%s" <dd> (F) You specified a signal name to the kill() function that was not recognized. Say kill -l in your shell to see the valid signal names on your system. </dd> <dt>Unrecognized switch: -%s <dd> (F) You specified an illegal option to Perl. Don't do that. (If you think you didn't do that, check the #! line to see if it's supplying the bad switch on your behalf.) </dd> <dt>Unsuccessful %s on filename containing newline <dd> (W) A file operation was attempted on a filename, and that operation failed, PROBABLY because the filename contained a newline, PROBABLY because you forgot to chop() or chomp() it off. See perlfunc/chop. </dd> <dt>Unsupported directory function "%s" called <dd> (F) Your machine doesn't support opendir() and readdir(). </dd> <dt>Unsupported function %s <dd> (F) This machines doesn't implement the indicated function, apparently. At least, Configure doesn't think so. </dd> <dt>Unsupported socket function "%s" called <dd> (F) Your machine doesn't support the Berkeley socket mechanism, or at least that's what Configure thought. </dd> <dt>Unterminated <> operator <dd> (F) The lexer saw a left angle bracket in a place where it was expecting a term, so it's looking for the corresponding right angle bracket, and not finding it. Chances are you left some needed parentheses out earlier in the line, and you really meant a "less than". </dd> <dt>Use of $# is deprecated <dd> (D) This was an ill-advised attempt to emulate a poorly defined awk feature. Use an explicit printf() or sprintf() instead. </dd> <dt>Use of $* is deprecated <dd> (D) This variable magically turned on multiline pattern matching, both for you and for any luckless subroutine that you happen to call. You should use the new //m and //s modifiers now to do that without the dangerous action-at-a-distance effects of <A HREF="perlvar.html#perlvar_382">$*</A> . </dd> <dt>Use of %s is deprecated <dd> (D) The construct indicated is no longer recommended for use, generally because there's a better way to do it, and also because the old way has bad side effects. </dd> <dt>Use of implicit split to @_ is deprecated <dd> (D) It makes a lot of work for the compiler when you clobber a subroutine's argument list, so it's better if you assign the results of a split() explicitly to an array (or list). </dd> <dt>Use of uninitialized value <dd> (W) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign an initial value to your variables. </dd> <dt>Useless use of %s in void context <dd> (W) You did something without a side effect in a context that does nothing with the return value, such as a statement that doesn't return a value from a block, or the left side of a scalar comma operator. Very often this points not to stupidity on your part, but a failure of Perl to parse your program the way you thought it would. For example, you'd get this if you mixed up your C precedence with Python precedence and said </dd> <pre> $one, $two = 1, 2; </pre> when you meant to say <pre> ($one, $two) = (1, 2); </pre> <dt>Warning: unable to close filehandle %s properly. <dd> (S) The implicit close() done by an open() got an error indication on the close(0. This usually indicates your filesystem ran out of disk space. </dd> <dt>Warning: Use of "%s" without parens is ambiguous <dd> (S) You wrote a unary operator followed by something that looks like a binary operator that could also have been interpreted as a term or unary operator. For instance, if you know that the rand function has a default argument of 1.0, and you write </dd> <pre> rand + 5; </pre> you may THINK you wrote the same thing as <pre> rand() + 5; </pre> but in actual fact, you got <pre> rand(+5); </pre> So put in parens to say what you really mean. <dt>Write on closed filehandle <dd> (W) The filehandle you're writing to got itself closed sometime before now. Check your logic flow. </dd> <dt>X outside of string <dd> (F) You had a pack template that specified a relative position before the beginning of the string being unpacked. See perlfunc/pack. </dd> <dt>x outside of string <dd> (F) You had a pack template that specified a relative position after the end of the string being unpacked. See perlfunc/pack. </dd> <dt>Xsub "%s" called in sort <dd> (F) The use of an external subroutine as a sort comparison is not yet supported. </dd> <dt>Xsub called in sort <dd> (F) The use of an external subroutine as a sort comparison is not yet supported. </dd> <dt>You can't use <A HREF="perlrun.html#perlrun_352">-l</A> on a filehandle <dd> (F) A filehandle represents an opened file, and when you opened the file it already went past any symlink you are presumably trying to look for. Use a filename instead. </dd> <dt>YOU HAVEN'T DISABLED SET-ID SCRIPTS IN THE KERNEL YET! <dd> (F) And you probably never will, since you probably don't have the sources to your kernel, and your vendor probably doesn't give a rip about what you want. Your best bet is to use the wrapsuid script in the eg directory to put a setuid C wrapper around your script. </dd> <dt>You need to quote "%s" <dd> (W) You assigned a bareword as a signal handler name. Unfortunately, you already have a subroutine of that name declared, which means that Perl 5 will try to call the subroutine when the assignment is executed, which is probably not what you want. (If it IS what you want, put an & in front.) </dd> <dt>[gs]etsockopt() on closed fd <dd> (W) You tried to get or set a socket option on a closed socket. Did you forget to check the return value of your socket() call? See perlfunc/getsockopt. </dd> <dt>\1 better written as $1 <dd> (W) Outside of patterns, backreferences live on as variables. The use of backslashes is grandfathered on the righthand side of a substitution, but stylistically it's better to use the variable form because other Perl programmers will expect it, and it works better if there are more than 9 backreferences. </dd> </dl>